You can apply profiles at both the tenant and port levels.
The following diagram illustrates how concurrent profiles are applied at different levels in a hierarchy and how they affect system configuration. The QoS profiles applied to individual interfaces have the highest priority, while those applied to the fabric level have the lowest priority. If no profile is applied on an interface, the default settings at the system level will be used.
% efa policy qos profile [bind | unbind] --profile <qosProfileName> --fabric|tenant <fabric-name|teannt-name>
% efa policy qos profile [bind | unbind] --profile <qosProfileName>
--fabric <fabricName>
indicates the specified profile is being applied to a set of interfaces belonging to the
specified fabric.Use the QoS profile command to:
Example:
% efa policy qos profile bind --profile fabricProfile1 --fabric fabric1
% efa policy qos profile unbind --profile fabricProfile1 -–fabric fabric1
% efa policy qos profile [bind | unbind] --profile <qosProfileName>
--tenant
<tenantName>
= This indicates the specified profile is being
applied to a set of interfaces belonging to the specified tenant.--port “IP[ifName,ifName
...], IP[ifName, …]”
- This parameter is optional and only used to
associate a policy to a subset of interfaces within a tenant. IP[ifName,ifName...]
- This is an identifier of the device and interface on which the specified
policy is to be applied. ifName
- This is an
abbreviated name of standard interface types. For example, eth = ethernet
. The
ifName
can
contain a comma separated list of interfaces on the device. For example,
1.1.1.1[0/1,0/2].Use the QoS profile command to:
– interface
option
or to a subset of interfaces within the tenant by providing a list of the
interfaces using the – interface option.Example of bind operation:
% efa policy qos profile bind --profile tenantProfile1 --tenant tenant1
efa policy qos profile bind --profile fabricProfile1 --fabric fabric1
efa policy qos profile bind --profile fabricProfile2 --fabric fabric1 --port “fabric-internal”
efa policy qos profile bind --profile tenantProfile1 --tenant tenant1
Example fo unbind operation:
efa policy qos profile unbind --profile fabricProfile1 -–fabric fabric1
efa policy qos profile unbind --profile tenantProfile1 --tenant tenant1
efa policy qos profile unbind --profile tenantProfile2 --tenant tenant1 –-port “1.1.1.1[0/1]” --po po3,po4
This topic describes examples on configuring fabric, tenants and QoS profiles and illustrates how the binding of QoS profiles within the binding hierarchy operates.
Example: To start the base configuration, a Fabric1 is created that contains Ethernet interface Eth0/1-Eth0/11. There are also three QoS profiles created, Profile1-Profile3 that have not yet been bound at any level in the hierarchy.
|
Example: To start the base configuration, a Fabric1 is created that contains Ethernet interface Eth0/1-Eth0/11. There are also three QoS profiles created, Profile1-Profile3 that have not yet been bound at any level in the hierarchy. After the configuration, the only allowable options are either to bind a profile to Fabric1 or create tenants and apply profiles to those tenants.
|
The following is the initial configuration for the two example is as follows.
% efa policy qos profile bind --profile Profile1 --fabric fabric1 % efa policy qos profile bind --profile Profile2 --tenant tenant3 % efa policy qos profile bind --profile Profile3 --tenant tenant1 --port “1.1.1.1[0/1,0/2]” % efa policy qos profile bind --profile Profile3 --tenant tenant2 --port “1.1.1.1[0/5]” % efa policy qos profile bind --profile Profile3 --tenant tenant3 --port “1.1.1.1[0/9]"--po "po3,po4”
Example:
efa policy qos profile unbind --profile Profile3 --tenant tenant3 --port “1.1.1.1[0/9]”The configuration of “Profile3” is removed from Eth0/9. Eth0/9 is reconfigured to contain the QoS configuration contained in “Profile2” as eth0/9 is a member of Tenant3, and Tenant 3 has Profile2 actively applied.
efa policy qos profile unbind --profile Profile2 --tenant tenant3The configuration of “Profile2” is removed from Eth0/7, Eth0/8, Eth0/10, and Eth0/11. These four interfaces will be reconfigured to contain the QoS configuration contained in “Profile1”.
Note
Since Profile3 is applied to Eth0/9 using the –-interface option when removing the Tenant3 binding even though Eth0/9 is member of Tenant3, the configuration of Eth0/9 is unchanged and still contains the configuration associated with Profile3.